pp108 : Log Message Search Parameters

Log Message Search Parameters

This topic describes the search parameters used to lookup log messages.

Field Name

Description

Example

Hop Count

Defines the number of hops in the 'request-flow'. Every time a service-container invokes another service container, the counter is incremented.

1

Timestamp

Mentions the time of log message occurrence.

02/05/2008 09:44:08.57

Severity

This field defines the degree of information required by a user about a log message.

Error

Thread

Specifies the thread at the Service Group, that invoked the log-message.

socket:
cin0321l:44608/Worker-1

Correlation ID

This refers to the unique Transaction ID which is propagated across the request flow.

b3838240-e0e7-4a9c-a822-6cb9865dd5e2

Localizable Message ID

The translatable unique ID of the log message .

Cordys.ESBServer.Messages.soapProcessorStarted

Category

Log messages are classified into a set of categories which help the user map the priority level.

com.eibus.xform.util.XFormsService

Application

The Application name where the web-service has been implemented.

Cordys ESBServer

User

The organizational user DN who initiated the SOAP request.

cn=test,cn=organizational users,o=system,cn=cordys,cn=defaultinst,o=vanenburg.com

Service Container

The Service Container where the log message occurred.

cn=XForms,cn=XForms,cn=soap nodes,o=system,cn=cordys,cn=defaultinst,o=vanenburg.com

Throwable

Specifies the exception occurred.

com.eibus.xml.nom.XMLException: Unable to perform operation:Node.delete() at com.eibus.xml.nom.Node.delete(Native Method) at com.eibus.xml.nom.Node.delete(Node.java:468) at com.cordys.cws.internal.util.nom.XmlNomNodeManagerImpl$NomNodeWrapper.clear(XmlNomNodeManager.java:87) at com.cordys.cws.internal.util.nom.XmlNomNodeManagerImpl.clear(XmlNomNodeManager.java:227) at com.cordys.cws.internal.util.nom.XmlNomNodeManager$1.releasedInstance(XmlNomNodeManager.java:31) at com.cordys.cws.internal.util.nom.XmlNomNodeManager$1.releasedInstance(XmlNomNodeManager.java:20) at com.cordys.cws.context.SubjectObserverHelper.releaseInstance(SubjectObserverHelper.java:91) at com.cordys.cws.context.SubjectObserverHelper.access$000(SubjectObserverHelper.java:23) at com.cordys.cws.context.SubjectObserverHelper$ObserverHelper.releaseContext(SubjectObserverHelper.java:106) at com.cordys.cws.internal.context.ObserverSubject$ObserverInstance.release(ObserverSubject.java:43) at com.cordys.cws.internal.context.ObserverSubject.release(ObserverSubject.java:87) at com.cordys.cws.session.SessionManager$SessionImpl.releaseInternal(SessionManager.java:204) at com.cordys.cws.session.SessionManager$SessionImpl.release(SessionManager.java:184) at com.cordys.cws.session.SessionManager.releaseSession(SessionManager.java:617) at com.cordys.cws.internal.operation.CustomOperationThread.run(CustomOperationThread.java:195) 

Localizable Message

The XML representation of the localizable message

WSDLException occurred while reading definition <cordys:LocalizableMessage xmlns:cordys=

"http://schemas.cordys.com/General/1.0/"> <cordys:MessageCode>Cordys.ESBServer.Messages.soapProcessorStarted</cordys:MessageCode> <cordys:Insertion>cn=Auditing,cn=Auditing,cn=soap nodes,o=system,cn=cordys,cn=build434,o=vanenburg.com</cordys:Insertion> </cordys:LocalizableMessage> 

Diagnostic Context

This fields serves as an identifier to extract the log messages in a given context.

The Diagnostic context added by a logger context is placed here in name-value pairs.

The XForms invoking this request flow can be identified by the prefix, 'XForms='. So in the given example the XForms can be deduced as '/logviewer/CALViewer.caf'. XForms=/logviewer/CALViewer.caf host=CIN0321l messageID=269AF5D8-331D-470B-9BE6-B3A186410EC6 processid=7772 Method=Restart


Related concepts

Logger Context

Related tasks

Viewing Log Messages using the Cordys Log Viewer

Related information

Composite Application Logging